The bootmanager BOOTMENU offers you the following functions: d
SEVERAL DOS / Windows VERSIONS (3.1x, 9x and NT) parallel on one or
several hard disk drives
UNLIMITED support of ALL operating and ALL file systems (as well as Win
98 and FAT32)
DISTINCTIVE SECURITY FEATURES for entire partitions using PASSWORDS and
"true" hiding
Unique extension from 4 up to 15 PRIMARY PARTITIONS (operating systems)
While computer is booting, freely selectable booting from ANY HARD DISK
DRIVE / disk
Problem-free integration of subsequent bootmanagers (e.g., LILO,
NTLoader...)
SETUP PROGRAMS for DOS and for WINDOWS 9X/NT
much more...
SEE ALSO: L
Works
(Overview)
System
Requirements
Security
Features
(Overview)
System Requirements
In order to be able to use the bootmanager BOOTMENU, you will need an Intel-compatible 80386 PC (or later model).
ALL operating systems and ALL file systems are supported, since the bootmanager's How It Works is not dependent on the operating and/or file system.
There are two setup programs: One for DOS (starting with version 4.0) and one for Windows (starting with Windows 95 / NT 3.51).
SEE ALSO:
Short
Overview
Works
Security
Features
Problem
(Overview)
Problems
Windows
3.1x/9x
Problems
Windows
Problems
Linux
How it works (Overview)
The bootmanager BOOTMENU manages two partitiontables: H
The master boot record partitiontable
The BOOTMENU partitiontable
The master boot record partitiontable is a table describing the subdivision of the hard disk drive into partitions. This table has been defined since the advent of hard disk drives during the beginning of the 80s and is absolutely required by all operating systems. This table can encompass up to four primary partitions.
The bootmanager BOOTMENU manages a second partitiontable internally (invisible to other programs / operating systems) with up to 15 entries. This table is called the "BOOTMENU partitiontable." 4
While the computer is booting, up to four entries are copied by the bootmanager BOOTMENU with the aid of the boot images. These entries are copied from the internal BOOTMENU partitiontable to the master boot record partitiontable. The remaining entries of the master boot record partitiontable are deleted.
The bootmanager is located on the hard disk on the first cylinder ("track 0"). This location is used by a few hard disk drivers and bootmanagers. Therefore, the capacity of your hard disk is not limited by the bootmanager BOOTMENU.
WHILE THE BOOTMANAGER BOOTMENU IS INSTALLED, NO OTHER HARD DISK DRIVE PARTITIONER MAY BE USED (E.G., FDISK OR PARTITIONMAGIC)!
SEE ALSO: J
Master
Record
Bootmanager
BOOTMENU
Boot
Images
Security
Features
Master Boot Record
The master boot record is the first sector on the hard disk drive. r
It contains the "bootstrap." This is a program, which is called by the BIOS to load the actual operating system. @
This sector also contains a description of how the hard disk drive is divided into separate areas (partitions). This description is listed in the so-called "partitiontable." It contains one entry for each partition. The entry lists the location of the partition on the hard disk drive and the "type" of this partition. P
Due to historical reasons, this partitiontable can include only four entries.
The format of this master boot record (bootstrap / partitiontable) is permanently defined and is ABSOLUTELY required by all operating systems.
SEE ALSO: Y
Partition
Types
Bootmanager
BOOTMENU
Open
Master
Record
Save
Master
Record
Bootmanager BOOTMENU
The bootmanager BOOTMENU is an independent bootstrap program. Thus, it is not dependent on the setup program. However, it will be generated by this setup program automatically during installation and written to the hard disk drive. V
This bootstrap (bootmanager) makes it possible to select a boot image while booting.
WHILE THE BOOTMANAGER BOOTMENU IS INSTALLED, NO OTHER HARD DISK DRIVE PARTITIONER MAY BE USED (E.G., FDISK OR PARTITIONMAGIC)!!!
SEE ALSO: ,
Installing
Boot
Image
Master
Record
Boot Images
While the computer is booting, you do not just use the bootmanager BOOTMENU to select an operating system (or a partition) but rather an entire boot image. This boot image contains the following settings:
Visible partitions: p
You may mark up to four of the fifteen primary partitions as "visible." The
remainder will be "truly" hidden.
Active partition: H
You may choose which of the visible partitions should be booted. In this
case, it is unimportant which hard disk drive contains this partition. It
is also possible to boot from disk as an alternative. (An additional option
is to change to booting from disk while the computer is already going
through the booting process.)
Order of the visible partitions: p
You may change the order of the partitions. This may be used to influence
the drive designation (e.g.: "C:").
Keyboard buffer:
You may write up to 16 automated keys into the keyboard buffer. This may be
used, for example, to control subsequent bootmanager such as LILO or
NTLoader.
Security settings:
You may indicate the following separate entries for each boot image:
whether it may also be booted from disk,
whether a password is required for booting, or
whether this boot image should be displayed at all.
SEE ALSO: :
Edit
Image
Bootmanager
BOOTMENU
Security
Features
Security Features (Overview)
The bootmanager BOOTMENU offers your data (partitions) a high level of security.
Due to the extension of the second partitiontable (BOOTMENU partitiontable) and the boot image concept, partitions from the master boot record partitiontable will be deleted.
Since these deleted partitions are no longer listed in the master boot record partitiontable, they cannot be seen by other hard disk drive partitioners either. Thus, they are "truly" hidden. Almost all other bootmanagers change nothing more than the partition type, which then can be changed back without any problems; it also means that the partitions are not hidden with only the access being restricted. (The encoded BOOTMENU partitiontable is invisible to other hard disk drive partitioners.)
The visibility of the partitions may be "switched on" using the boot images. These may be protected individually using passwords, so that no one without the proper password may have access to your data.
Furthermore, it is also possible to hide boot images, so that these may only be offered after a specific key combination has been used. Thus, a non-authorized person cannot even detect, whether additional boot images (partitions) even exist. G
Booting from disk may also be permitted or restricted via a password.
The reliability of such a protection and safeguarding of the partitions has a high rating, since probably only about 0.1% of all users is able to circumvent this type of password protection.
SEE ALSO: c
Works
Security
Features
Application
Security
Features
Boot
Images
Edit
Image
How it works of the Security Features
The bootmanager BOOTMENU does not protect your partitions but your boot images. The principle applied is the same as for the distribution of rights on the Internet. There too passwords are required when registering, with these passwords then referencing certain various resources.
Thus, it follows that if you want to protect a partition on your computer, you have to protect all those boot images with a password that contain these partitions.
In some cases, a boot image is created solely for the system administrator. Such a boot image should be hidden completely. It will be displayed only after a specific key combination (hot key) has been pressed. This function may be activated separately for each boot image.
You should definitely protect the bootmanager BOOTMENU itself with a password, so that none of the users can view or even change the settings after downloading the setup program (from the Internet).
SEE ALSO:
Security
Features
(Overview)
Application
Security
Features
Boot
Images
Edit
Security
Settings
BOOTMENU
Settings
BOOTMENU
Password
Application of the Security Features
While booting (after selecting boot image), the bootmanager BOOTMENU fills the master boot record partitiontable with the partitions to be used.
These partitions are temporarily unprotected, because they can be (and are supposed to be) seen by all users and operating systems.
In order to protect the partitions again, the entries from the master boot record partitiontable have to be deleted again. This can be done in two ways: {
1. Booting the computer (partitions are deleted when BOOTMENU is started)
2. Calling the setup program using "/ClearMBR"
Operating systems read the partitiontable only during booting. Therefore, the setup program may already be called in the "AUTOEXEC.BAT" file. The computer will then remain protected if not newly rebooted. 5
The booting sequence in the BIOS should ALWAYS be "C:, A:," and the BIOS should ALWAYS be protected by a password. This will prevent that a user does not boot from disk without having authorization to do so. However, booting from disk may still be possible if you permit it with the aid of the boot images. 4
Modifying the booting sequence also ensures that the bootmanager BOOTMENU will always be called and that the entries from the master boot record partitiontable are thus deleted. (This is only reliable if the hard disk drive will not be taken out of the computer and then reinstalled into another computer.)
SEE ALSO: m
Overview
Security
Features
Works
Security
Features
Boot
Images
Master
Record
Installation (Overview)
Unzip the file "BOOTMENU.ZIP". It contains the following files: S
BMDOS.EXE Setup program for DOS (starting with version 4.x)
BMDOS.HLP Help file with detailed description for DOS
BMWin.exe Setup program for Windows 95 / Windows NT (starting with
3.51)
BMWin.dll Supplement for the Windows setup program
BMWin.hlp Help file with detailed description for Windows
BMWin.cnt Supplement for the Windows help file
ReadMe.txt Brief description of the bootmanager
Manual.pdf Manual in Adobe Acrobat Portable Document Format
Order.txt Order form for orders via mail / fax
FILE_ID.DIZ Brief description of the zipped file
Both setup programs are completely compatible. The only difference is the operating system (DOS / Windows) under which they can be started. All other items (functionality and menu structure) are completely identical. W
After all files have been unzipped, you can start the correct setup program directly.
However, you should first plan your system well, because it is very difficult to modify the configuration (partitions) at a later time.
SEE ALSO:
Planning
System
Installation
System
Installation
Existing
System
Installation
Operating
System
Configuration
Images
Planning a System
BEFORE you begin with the installation of the bootmanager or operating system, you should think about how you would like to organize your system: c
Most important is here that you will FIRST decide which operating systems you would like to use.
The next step should be determining how much hard disk space is required by which operating system (size of the hard disk). The manufacturer of the operating system usually already suggests a certain size, which you should use as your minimum.
It might be beneficial to reserve a part of your hard disk drive (a partition) to make data available for all or at least several operating systems.
It is best to leave some part of your hard disk drive unused (if it is large enough), so that you can use this part for later extensions. H
IT IS VERY DIFFICULT TO RECONFIGURE A SYSTEM ONCE IT HAS BEEN SET UP.
Each operating system should have its own partition. You can use the bootmanager BOOTMENU to manage up to 15 partitions per hard disk.
It is also possible to boot most of the operating systems from the 2nd hard disk drive (or higher), so that you might want to think about which operating system you would like to install on which hard disk. (The bootmanager BOOTMENU supports up to four hard disk drives.)
Finally, the last step should consist of deciding which operating system is supposed to "see" which partitions, and which partitions should be hidden. i
Some operating systems have limitations regarding booting and visibility, which have to be observed: O
Problems
Windows
Problems
Windows
Problems
Linux
One you have decided how to set up your system, you should then install the bootmanager BOOTMENU on the hard disk drive(s). It is advisable to install the bootmanager BOOTMENU BEFORE installing the operating system(s), so that the separation of the operating systems functions better. >
Installation
System
Installation
Existing
System
The you need to configure the boot images:
Configuration
Images
Finally, install the operating system(s): "
Installation
Operating
System
Installation on New System
Installing the bootmanager BOOTMENU on a new system is very easy. All you have to do is start the setup program. The setup program will ask you immediately whether you want to install the bootmanager. Answer with "Yes."
Then your are asked to backup the master boot record as a file for safeguarding purposes. (If a system really is brand-new and has not been used yet, then this backup is not necessary.) !
Then configure the boot images:
Configuration
Images
Done!
SEE ALSO:
Installation
(Overview)
Installation
Operating
System
Master
Record
Positions
General
Problems
Limitations
Problems
Windows
3.x/9x
Problems
Windows
Problems
Linux
Installation on Existing System
It is very easy to install the bootmanager BOOTMENU on an existing system: Simply start the setup program. You will be asked whether you would like to install the bootmanager. Answer with "Yes."
Then you will be asked to save the master boot record as a file for safeguarding purposes. You should seriously consider doing so, because otherwise you cannot restore your system 100% if any problems should occur.
After the installation is complete, the boot image table will appear. Here you will now need to configure your boot settings:
Configuration
Images
SEE ALSO:
Installation
Overview
Installation
Operating
System
Master
Record
Positions
General
Problems
Limitations
Problems
Windows
3.x/9x
Problems
Windows
Problems
Linux
Installation of New Operating System
If you would like to install an operating system BEFORE you install the bootmanager BOOTMENU, you may disregard the following details!
INSTALLING OPERATING SYSTEMS AFTER THE BOOTMANAGER HAS BEEN INSTALLED ENABLES A BETTER SEPARATION AMONG THE OPERATING SYSTEMS. u
To install a new operating system while installing the bootmanagers BOOTMENU, please carry out the following steps:
Create a partition for the new operating system (see also details about
the partition types)
Create a boot image, which contains nothing but the just created
partition
Install the operating system (during the first booting, select the boot
image using <Ctrl+Enter> to boot from disk)
Call this setup program and configure the boot images according to your
wishes
If the new operating system is supposed to be installed from CD-ROM, please execute the following steps (the current level of BIOS technology does not permit any other solution):
Select boot image
Perform reset
Set the "boot sequence" in the BIOS to "A:, C:"
Install operating system
Return the "boot sequence" in the BIOS back to "C:, A:"
Select boot image
SEE ALSO:
Installation
(Overview)
Planning
System
Configuration
Images
Partition
Types
General
Problems
Limitations
Problems
Windows
3.x/9x
Problems
Windows
Problems
Linux
Partition Types
Almost each operating system uses its own file system to save its data. Recognition of the file system is triggered by the partition type. Thus, for each file system, the correct partition type has to be entered. (In this program, the partition type is indicated using a hexadecimal system.)
The following list can never be complete because every manufacturer of operating systems is basically able to define his or her own types at any time.
MS-DOS:
Up to version 3.3: Type "01"
Up to version 3.3 up to 32 megabytes: Type "04"
Up to version 3.3 with more than 32 megabytes: Type "06"
WINDOWS 95:
Normal: Type "06"
Use of "LBA" mapping: Type "0E"
Extended partition: Type "05"
Extended partition using "LBA" mapping: Type "0F"
WINDOWS 95B OSR 2, WINDOWS 98:
Partition < 32 megabytes: Type "04"
Normal: Type "06"
Partition > than 2 gigabytes or more than 2 gigabytes / FAT 32: Type "0B"
WINDOWS NT: _
Using FAT (can be read by DOS): Type "06"
Using NTFS (faster and long file names): Type "07"
OS/2: _
Using FAT (can be read by DOS): Type "06"
Using HPFS (faster and long file names): Type "07"
LINUX: a
Normal partition (ext2fs): Type "83"
Swap partition (should be set up additionally): Type "82"
EXTENDED PARTITIONS: <
Normal: Type "05"
Access via "BIOS extensions": Type "0F"
NOVELL NETWARE: 1
Netware 286: Type "64"
Netware 3.11: Type "65"
OTHER: *
If one partition type is not listed here, type "06" is usually suitable for
the installation of an operating systems. The type is often going to be
corrected automatically during the installation.
If needed, consult the manual of your operating system to obtain further
information and tips.
SEE ALSO: a
Installation
Operating
System
Select
Partition
Edit
Partition
Master
Record
Configuration of Boot Images
The boot images constitute the individual choices, which are offered to you by the bootmanager BOOTMENU while the computer is being booted. They contain all information needed for booting.
The minimum amount of information required in these boot images consists of which partition should be visible and which partition should be the boot partition (disk). a
These settings are inserted into the boot image table after the bootmanager has been installed.
The boot images can be reconfigured at ANY TIME WITHOUT ANY PROBLEMS, so that any extensive planning ahead of time is not necessary. You probably will change the settings of individual boot images at one or another or add new ones.
Please note that some operating systems (e.g., Windows NT and Linux) require the die exact position of your partition entry in the master boot record partitiontable. This has to be configured in the boot image under "Positions in MBR."
SEE ALSO:
Installation
Overview
Installation
Operating
System
Boot
Images
Boot
Image
Table
Security
Features
General
Problems
Limitations
Problems
Windows
3.x/9x
Problems
Windows
Problems
Linux
Updates
Updates are very easy: Start the setup program of the new version. This setup program will recognize automatically whether an update of the bootmanager BOOTMENU is required. After a query, it will update the bootmanager automatically.
It can happen that an update of the setup program does not require an update of the bootmanager. In this case, only the setup program has been improved.
If you have already registered your copy of the bootmanager, this registration will remain valid even after the update. However, the setup program will indicate that it is unregistered. This refers only to the setup program and has no effect on the bootmanager. w
You can obtain updates on the Internet via the homepage of the bootmanager BOOTMENU. Currently, all updates are FREE!
SEE ALSO: '
Installation
(Overview)
Order
Uninstallation
The uninstallation of the boot manager program BOOTMENU is as easy as the installation: Just start the setup program and choose the menu item "BOOTMENU / Uninstallation". (Nils, ich kann mich jetzt nicht erinnern, ob wir als Men
punkt Deinstallation oder Uninstallation genommen haben.)
Of course, the uninstallation is only possible if not more than 4 primary partitions have been set up. The reason is that all partitions have to be entered into the partition table of the master boot record. ]
A "default" bootstrap is written into the master boot record during the uninstall process.
If you require exactly the same conditions after the uninstall process as existed before the installation, you can open the master boot record from the file you created during installation.
SEE ALSO: V
Installation
(Overview)
Installation
System
Installation
Existing
System
Command Line Options (Overview)
All functions of this setup program may also be called from within "batch files" using so-called "command options." This is of special interest to companies that have to perform many installations. H
Indicates whether BOOTMENU has been installed on the hard disk.
Return:
If BOOTMENU is installed: number of installed boot images; otherwise "0"
(zero).
/MBR '
Reinitializes the bootstrap in the master boot record. If BOOTMENU is
installed, BOOTMENU generates the bootstrap. Otherwise, a default bootstrap
will be generated.
If BMDOS.EXE was registered, the registration also released the bootmanager
BOOTMENU for use.
Return:
"1," if successful.
/CLEARMBR
Deletes die MBR partitiontable(s). While BOOTMENU is installed, the MBR
table of all hard disk drives on which BOOTMENU is installed will be
deleted. Otherwise, only on the indicated hard disk drive.
Return:
"1," if successful.
/PARTITION
Indicates the active partitiontable. While BOOTMENU is installed, the
BOOTMENU partitiontable will be displayed. Otherwise, the MBR
partitiontable will be displayed.
Return:
Number of existing partitions.
/PARTITION:N
Activates the nth partition.
This parameter may only be used if BOOTMENU is not installed.
Return:
"n," if partition exists.
/PARTITION:NNN-S
Adds a new partition. If needed, a new boot image will be created for this
partition, which contains only this additional partition.
NNN is the name of the boot image, s is the size in megabytes.
The "-" has to be entered.
Return:
Number of partitions after the addition.
/BOOTIMAGE |
Displays the boot image table. Functions only if the bootmanager BOOTMENU
is installed.
Return:
Number of boot images.
/BOOTIMAGE:N
Activates the nth boot image. Functions only if the bootmanager BOOTMENU is
installed.
Return:
"n," if the boot image exists.
/BOOTIMAGE:FILE
Loads the boot image table from the file "file." All already existing boot
images will be deleted.
Return:
Number of boot images.
/TIME:N
Indicates in seconds the time that will elapse until booting. Functions
only if the bootmanager BOOTMENU is installed.
Return:
Time in seconds (255, if deactivated).
/TIME:OFF H
No automatic booting.
Return:
Time in seconds (255, if deactivated).
/REBOOT
Reboots the system (reset).
/PASSWORD:PPP-NNN
Permits calling the program and, if needed, creates a new password. This
command might have to be issued first!
PPP: Password for this program
NNN: New password for this program
Return:
"1", if incorrect password was indicated.
/HIDDEN +
Suppresses screen output.
Return:
None.
/FILE[:FILE]
Reads commands from file. Details in the following section.
Return:
Taken over by last command or "0," if the file "file" was not found.
Displays this help.
Return:
"1", if BOOTMENU is active.
It is not necessary to write out all option in their entirety; it suffices to indicate the respective first letter (insofar as the first letter is unambiguous).
When indicating the hard disk drive (e.g., ",HDD2") it suffices to type in the number of the hard disk drive (example: ",2"). If nothing is entered, then the first hard disk drive will be used. b
All entries start with "1" (e.g., 1st hard disk drive: ",HDD1"; 1st partition: "/partition:1"). U
The return value "0" (zero) always refers to an error (if not indicated otherwise).
SEE ALSO: ,
Script
Return
Values
Using
Script File
An alternative to indicating all commands in a batch file is the "script file." More details about the commands can be obtained in the section Command Options. Script files should have the extension "*.scr." Within this file, all commands written in command option lines are indicated with "/." O
Only one command may be written within one line. Commentaries start with ";." E
If no file name is indicated, then the file BMDOS.SCR will be used.
The command "Hidden" should not be used in the script file, because output will not be suppressed until this command has been called.
SEE ALSO: 5
Command
Options
Return
Values
Using
Return Values Using Exitcode
The return values within a batch file can be handled as follows: B
INSTALL.BAT:
BMDOS.EXE /Install
If Errorlevel 1 Goto NUMBER
Echo INSTALL.BAT: Error during installation !
Goto Ende
:NUMBER
BMDOS.EXE /partition
If Errorlevel 3 Goto LABEL3 ; The sequence must always
If Errorlevel 2 Goto LABEL2 ; view the highest Errorlevel
If Errorlevel 1 Goto LABEL1 ; first!
Echo INSTALL.BAT: No partitions exist!
:LABEL1
Echo INSTALL.BAT: One partition exists!
Goto ENDE
:LABEL2
Echo INSTALL.BAT: Two partitions exist!
Goto ENDE
:LABEL3
Echo INSTALL.BAT: Three or more partitions exist!
Goto ENDE
:ENDE
Additional information about batch programming is listed in the manual of the DOS operating system.
SEE ALSO: #
Script
Command
Options
Problems (Overview)
For most operating systems, it might be necessary to set the hard disk
drive in the BIOS to the "LBA" mode.
Some SCSI hard disk drives might require that the ASPI driver is loaded
before starting the setup program of the bootmanager BOOTMENU.
Adaptec SCSI hard disk drives should be deactivated with the "Int 13 BIOS
Extension Support."
Hard drives, which need a software driver (either because of their size
and/or age) usually cannot be used with the bootmanager BOOTMENU.
The bootmanager BOOTMENU is written into the first cylinder (track 0) of
the respective hard disk drive. That is the reason the program cannot be
used with other programs (usually also bootmanagers), which occupy and
use the same memory location.
SEE ALSO: T
Problems
Windows
3.1x/9x
Problems
Windows
Problems
Linux
Problems with DOS / Windows 9x
GENERAL:
For MS-DOS and Windows 95 (not Windows 95b OSR 2), the maximum partition
size is 2 Gigabytes.
For MS-DOS up to version 6.2x, booting can only take place if the boot
partition starts within the first 2 Gigabytes on the hard disk drive.
For MS-DOS up to version 4.x, only one primary partition (boot image) at
one time may be visible. (However, it is not a problem to install
several.).
It is possible to boot from the 2nd harddisk only if no primary
partition is visible on the 1st harddisk.
INSTALLATION:
The setup program of Windows 9x writes over the master boot record during
installation. This damages the bootmanager BOOTMENU. Therefore, after the
installation, the file setup program of the bootmanager BOOTMENU should be
executed in order to correct the error automatically.
INSTALLATION ON SECOND HARD DRIVE:
When installing on the second hard drive, the power has to be disconnected
to the first hard drive during the installation process.
An alternative is to "manually" install DOS (with FORMAT, SYS, and COPY).
SEE ALSO: D
Problems
(Overview)
Problems
Windows
Problems
Linux
Problems with Windows NT
GENERAL: 3
If Windows NT is supposed to be installed on the hard drive above 2
Gigabytes, the partition has to be formatted with Windows 95 before the
installation.
Only one Windows NT partition (boot image) may be visible at any one
time. (However, more than one can be installed without any problems.
NTLOADER - BOOT.INI:
The file BOOT.INI contains the information on which partition Windows NT is
installed. In this case the information concerns the position of the
partition in the partitioning table of the master boot record (empty
entries are only counted while bootmanager BOOTMENU is installed). That
means that the master boot record partitiontable and the file BOOT.INI from
Windows NT have to be in agreement with one another.
The position in the master boot record partitiontable can be set in the
boot image ("Positions in MBR").
The position in the BOOT.INI can be set as follows:
If necessary, all entered specifications have to be corrected! The entered
specification for the first hard disk drive is a "0" (zero).
SEE ALSO: J
Problems
(Overview)
Problems
Windows
Problems
Linux
Problems with Linux
GENERAL: V
Linux can only be booted if the partition starts on a cylinder before
cylinder1024.
LILO KEYBOARD CONTROL:
In order to transfer keyboard entries from the bootmanager BOOTMENU to
LILO, it is necessary for some distributions to build LILO with a specific
option. For more details about this subject, please read then LILO
documentation.
LILO CONFIGURATION - LILO.CONF:
The file lilo.co contains the information on which partition Linux is
installed. This information refers to the position of the partition in the
master boot record partitiontable. (Empty entries are only counted while
the bootmanager BOOTMENU is installed.) Thus, the master boot record
partitiontable and the file lilo.conf from Linux have to be in agreement
with one another.
The position of the respective partition can be set in the boot image.
The position of the file lilo.conf can be set as follows:
boot = /dev/hda1 ; IDE hard disk drive
boot = /dev/sda1 ; SCSI hard disk drive
The specification "hda1" and/or "sda1" is decisive. If necessary, all
entered specifications have to be corrected! The entered specification for
the first partition is a "1".
SEE ALSO: O
Problems
(Overview)
Problems
Windows
Problems
Windows
Open File
SETUP PROGRAM:
BOOTMENU
Partitiontable / File / Open...
Master
Record
Partitiontable / File / Open...
Boot
Image
Table / File / Open...
Extended
Partitiontable / File / Open...
You may load the content of a currently visible window (..., table, or opening message) from a previously created file.
If you load a partitiontable, the old partitiontable will be completely overwritten with the new one. In case you are loading an outdated or invalid partitiontable, you may use this feature to overwrite partitions.
An opening message text may be loaded from a normal ASCII file. The tables have to be loaded from a file previously created with this program.
SEE ALSO:
Save
Save File
SETUP PROGRAM:
BOOTMENU
Partitiontable / File / Save...
Master
Record
Partitiontable / File / Save...
Extended
Partitiontable / File / Save...
Boot
Image
Table / File / Save...
You may save the content of a currently visible window in a data file. These files should be stored on a floppy disk if possible so that continuous access is guaranteed even if you should encounter problems (with accessing the hard disk drive).
All files are saved in an ASCII file without any encoding. This means you might want to consider protecting them from any unauthorized access.
SEE ALSO:
Open
Open Partition
SETUP PROGRAM:
BOOTMENU
Partitiontable / File / Open Partition...
Master
Record
Partitiontable / File / Open Partition...
Extended
Partitiontable / File / Save...
You may load the contents of an entire partition from a previously saved file. In this case, the entire contents of the partition will be deleted and overwritten with the contents of the partition from file. S
The partition is selected by making the appropriate choice in the partitiontable.
SEE ALSO:
Save
Partition
Save Partition
SETUP PROGRAM:
BOOTMENU
Partitiontable / File / Open Partition...
Master
Record
Partitiontable / File / Open Partition...
Extended
Partitiontable / File / Save...
You may store the content of a currently selected entire partition in a file for the purpose of restoring it at a later time. Backup is performed regardless of the contents of the partition. (E.g., the long file names of Windows 9x remain intact.) p
The file system of the partition is disregarded, which means that the created binary file will be very large.
This process can be used by companies with several computers constructed in the same fashion to copy the partitions from one computer to another. This will save a considerable amount of time.
However, the partitions can only then be loaded if the hard disk drives, the position of the partition on the hard disk drive, and the size of the partition are identical.
SEE ALSO:
Open
Partition
Open Master Boot Record
SETUP PROGRAM: 9
File / Open Master Boot Record... / nth Hard Disk Drive
You may load the content of the master boot record (incl. bootmanager) in its entirety from a previously created binary file (*.bms). (This file should have been created during installation.) )
In this case, you should make sure that the master boot record contains the bootstrap as well as the partitiontable and is written in its entirety from the partitiontable to the file of the master boot record. Loading an outdated or invalid partitiontable can result in the loss of partitions.
It rarely serves any purpose to load a master boot record. Should the restoration of the bootstrap be absolutely necessary, the following process might be helpful:
If needed, uninstall BOOTMENU.
Save master boot record partitiontable to file (*.bmt).
Open master boot record.
Open master boot record partitiontable from the file generated above
(*.bmt).
SEE ALSO: z
Save
Master
Record
Uninstall
BOOTMENU
Master
Record
Partitiontable
Open
Partitiontable
Save
Partitiontable
Save Master Boot Record
SETUP PROGRAM: 4
File / Master Boot Record... / nth Hard Disk Drive
You may save the entire master boot record (incl. any installed bootmanager) to a binary file (*.bms). This file may later be used to restore the master boot record exactly as it has been saved (e.g., after the bootmanager has been uninstalledSUnInstall).
SEE ALSO: -
Master
Record
Open
Master
Record
Edit Partition
SETUP PROGRAM: ^
BOOTMENU
Partitiontable / Edit / Edit...
Master
Record
Partitiontable / Edit / Edit...
The following settings have to / can be made for each partition:
Start:
Beginning of partition
End:
End of partition
Type: Y
Pressing the button "Selection" offers a list from which to choose the
partition type.
Name:
This field only appears with the BOOTMENU partitiontable. You may indicate
a name to make it easier to find the partition when setting up the boot
image.
The start and end specifications can only be indicated when a partition is being created. If you were to change these specifications for an existing partition, the installed file system would have to be changed as well. (This task exceeds the function of a bootmanager.) )
FAT partitions may be increased or decreased using a program such as FIPS (Freeware). This program was developed to divide existing DOS partitions without destroying the therein-contained data. FIPS may be obtained on the Internet. The URL is listed on the homepage of the bootmanager BOOTMENU.
SEE ALSO: s
BOOTMENU
Partitiontable
Master
Record
Partitiontable
Partition
Types
Select
Partition
CHS Encoding
Select Partition Type
SETUP PROGRAM:
Master
Record
Partitiontable / Edit / Edit... / Selection
BOOTMENU
Partitiontable / Edit / Edit... / Selection
Extended
Partitiontable / Edit / Edit... / Selection
A list will offer different partition types. Select the one based on the file system to be used. P
You may also select a partition type based on the operating system being used:
Partition
Types
SEE ALSO: L
Edit
Partition
BOOTMENU
Partitiontable
Master
Record
Partitiontable
Edit Boot Image
SETUP PROGRAM: #
Boot
Image
Table / Edit / Edit...
You may indicate the following settings for each boot image:
Name:
Enter the name of the boot image. This name will appear in the bootmanager
BOOTMENU during booting. (The boot image may then be selected by either
pressing the first letter of the name or by using the cursor keys.)
Boot Disk:
Enter the drive from which to load using this boot image. If you select a
hard disk drive, you have to indicate which partition should be active as
well.
Some operating systems support only the 1st disk and the 1st hard disk
drive. If you would like to boot from the 2nd hard disk drive (or higher),
most operating systems require that the previous hard disk drives do not
have any visible partitions.
Active:
Indicate the partition from which to boot. (You may only activate "visible"
partitions, which are located on the "boot disk.")
Here you will activate the extended partition and the secondary partition
within the extended partitiontable in order to boot from a secondary
partition.
Visible:
Enter up to four partitions you would like to make visible in this boot
image. During booting, these partitions are used by BOOTMENU to enter them
into the master boot record partitiontable. (The reason for the limitation
to only four partitions rests with the master boot record.)
SEE ALSO: e
Bootmanager
BOOTMENU
Edit
Security
Settings
Edit
Keyboard
Buffer
Positions
Master
Record
Edit Security Settings
SETUP PROGRAM: 7
Boot
Image
Table / Edit / Edit... / Security Settings
You may indicate the following security settings for each boot image:
Password:
Here you may enter a password required for the booting of this boot image.
This function may be used to protect partitions by indicating a password
for all boot images containing the partition to be protected.
Booting from Disk:
If you deactivate this option, it will be impossible to boot the selected
boot image from disk during the booting process using <Ctrl+Enter> instead
of <Enter> from BOOTMENU.
Visible Boot Image: <
If you deactivate this option, this boot image will not be displayed by
BOOTMENU during the booting process. Only after pushing the "hot keys" will
this boot image become visible and may then be selected. (The "hot keys"
may be changed in the "BOOTMENU Settings." Usually, <Alt+B>, <Alt+M> are
the "hot keys.")
SEE ALSO: X
Overview
Security
Features
Edit
Image
BOOTMENU
Settings
BOOTMENU
Password
Edit Keyboard Buffer
SETUP PROGRAM: <
BOOTMENU
Partitiontable / Edit / Edit... / Keyboard Buffer
You may indicate up to 16 characters for each boot image, which otherwise would have to be "manually" selected while booting. \
This allows for the integration of subsequent bootmanagers such as e.g., LILO or NTLoader.
Most of the keys may be specified in this field. The remaining keys (e.g., "Enter") may be specified if you press the "Scroll Lock" key. You may enter all keys until the "Scroll Lock" key has been pressed again. Bis P
(Please note that the American keyboard driver will be used during
It is possible to vary the positions of the individual partitions within the master boot record partitiontable. (These settings are reset each time a partition is changed or modified. In that case, it is necessary to re-enter the settings of the "Positions in MBR".) 9
This is necessary for some operating systems to ensure that they function properly (Windows NT and Linux). It might be possible therefore, that these operating systems expect the partition to be located in the exact same position in the master boot record as before the bootmanager BOOTMENU had been installed.
For most operating systems, the order of the partitiontables also determines the logical drive designation. This means that the order of the logical drive designation can be modified by changing the order of the entries in the partitiontable. _
Microsoft operating systems always require the following drive letter specification sequence:
1. Primary, active partition on 1st harddisk
2. Primary partitions on 2nd harddisk according to the "positions in the
MBR"
3. Secondary partitions on 1st harddisk according to order on hard drive
(cylinder, head, sector)
3. Secondary partitions on 2nd harddisk according to order on hard drive
(cylinder, head, sector)
4. Remaining partitions primary partitions on 1st harddisk according to
"Positions in MBR"
All additional harddisks are treated accordingly.
SEE ALSO: T
Master
Record
Problems
Windows
Problems
Linux
Edit
Image
Extended Partitiontable
SETUP PROGRAM: t
BOOTMENU
Partitiontable / Edit / Extended Partition
Master
Record
Partitiontable / Edit / Extended Partition
You may edit the extended partitiontable the same way as the master boot record and the BOOTMENU partitiontable.
If you would like to boot from a secondary partition, you have to activate that secondary partition within the extended partitiontable; then switch this extended partition from inactive to "active" in the boot image. |
Some operating systems do not support booting from secondary partitions at all or only if no primary partition is visible.
The functionality of the bootmanager, unfortunately, is not available to secondary partitions. The entire extended partition can be either only completely visible or completely invisible. The selection of the active partition cannot be set in the boot image either.
SEE ALSO: X
Edit
Partition
BOOTMENU
Partitiontable
Master
Record
Partitiontable
Boot
Image
Install BOOTMENU
SETUP PROGRAM:
BOOTMENU / Install
The installation process writes the actual bootmanager to the hard disk drive. During the process, entries of the master boot record partitiontable are copied and entered into the new BOOTMENU partitiontable and the bootstrap is overwritten with the bootmanager.
During the installation, you should choose to backup the master boot record to a file, so that you will be able to return the system -- after the uninstall process -- to the exact same condition it was before the installation.
BOOTMENU may be installed separately on every hard disk drive. If BOOTMENU is not installed on the first hard disk drive, the boot images can be selected only through the use of the command line options. s
WHILE BOOTMENU IS INSTALLED, NO OTHER HARD DISK DRIVE PARTITIONER MAY BE USED (E.G., FDISK OR PARTITIONMAGIC)!!!
SEE ALSO: g
Master
Record
Partitiontable
BOOTMENU
Partitiontable
Master
Record
Uninstalling
BOOTMENU
Uninstall BOOTMENU
SETUP PROGRAM:
BOOTMENU / Uninstall
You can uninstall the bootmanager BOOTMENU only if the BOOTMENU partitiontable of the corresponding hard disk drive does not have more than four partitions. (The reason for this is the format of the master boot records)
SEE ALSO:
Uninstallation
Master
Record
Installing
BOOTMENU
Open
Master
Record
BOOTMENU Partitiontable
SETUP PROGRAM: 1
BOOTMENU / Partitiontable / nth Hard Disk Drive
This table displays all (visible and invisible) partitions of the hard disk drive. :
The following parameters of the partition are displayed: N
Number (position) of the partition
Start / end of the partition (only the cylinder specifications are
indicated here. More details are obtained when editing the corresponding
partition)
Type of partition
Name of the partition (is only an internal program specification used to
facilitate the boot image settings)
SEE ALSO: s
Master
Record
Partitiontable
Extended
Partitiontable
Partition
Types
Edit
Partition
Open
Save
Boot Image Table
SETUP PROGRAM: 1
BOOTMENU / Partitiontable / nth Hard Disk Drive
This table lists all boot images: d
The name of the boot image is displayed on the very left hand side (will be shown during booting). .
This is followed by the existing partitions:
An "X" means that this partition is visible.
An "A" means that this partition is visible and active (this is the boot
partition).
On the very right hand, you will see whether a password has been specified for this boot image. 9
More details are available when editing the boot image.
SEE ALSO: 3
Boot
Image
Edit
Image
Open
Save
BOOTMENU Opening Message
SETUP PROGRAM:
BOOTMENU / Opening Message...
Here you may specify an opening message (any text), which will be displayed during the booting process and BEFORE a boot image is selected.
You can use the text message to present general information or information about the boot images to the user. You may use about 1 000 characters. K
(This function is mainly of interest for computers with different users.)
SEE ALSO: 0
BOOTMENU
Settings
BOOTMENU
Colors
Boot
Image
BOOTMENU Settings
SETUP PROGRAM:
BOOTMENU / Settings...
Here you may specify some general settings. which influence the functions of the bootmanager BOOTMENU while booting:
Auto-boot / Time:
Specify a time after which the auto-boot will start -- if the user does not
make a choice. Auto-boot will boot the active boot image.
Default Choice:
Choose, whether the same boot image should always be active or the
previously selected boot image:
Always the same: The default boot image is the one activated in the boot
image table.
Previous: The default is always the one chosen previously during the
last booting.
Boot Image Selection: K
Here you can activate or deactivate the display of the chosen boot image.
MBR Checksum:
Deactivate this option if you are using a hard disk driver, which requires
access to the master boot record.
While booting, a check is run on the master boot record in order to detect
any modifications (usually by viruses). If any modifications are found,
this setup program will be triggered, which then will (after confirmation)
reverse the modification (the virus is removed) automatically.
Hot Keys:
Indicate one or two keys to be pushed to receive a list of the invisible
boot images (Security Settings of the Boot Images) and to make a
selection.
SEE ALSO: d
Bootmanager
BOOTMENU
Boot
Image
Table
Edit
Security
Settings
BOOTMENU
Colors
BOOTMENU
Password
BOOTMENU Colors
SETUP PROGRAM:
BOOTMENU / Colors...
Here you may select the colors of BOOTMENU during booting. u
Change the color by first selecting the element color, then the foreground color, followed by the background color.
PLEASE NOTE (DOS VERSION): t
You may switch from one field to the next by using the <Tab> key. To chose
any color, please use the cursor keys.
SEE ALSO: )
Bootmanager
BOOTMENU
BOOTMENU
Settings
BOOTMENU Password
SETUP PROGRAM:
BOOTMENU / Password...
Here you may protect the entire bootmanager BOOTMENU (incl. all settings) with a password. U
If you specify a new password, a perhaps already existing password will be deleted.
PLEASE MAKE A NOTE OF THIS PASSWORD! IF YOU SHOULD FORGET THIS PASSWORD, IT WILL BE IMPOSSIBLE EITHER TO START THE SETUP PROGRAM OR TO UNINSTALL BOOTMENU! YOU ARE THEN ALSO LONGER ABLE TO VIEW OR MODIFY THE PARTITION INFORMATION.
SEE ALSO: .
Edit
Security
Settings
Bootmanager
BOOTMENU
Master Boot Record Partitiontable
SETUP PROGRAM: ;
Master Boot Record / Partitiontable / nth Hard Disk Drive
This table displays all partitions of the hard disk drive (while BOOTMENU is NOT installed). While BOOTMENU is installed, the current setting (selected boot image) is displayed.
You will see the following:
Active partition ("A")
Start / end of the partition (only the cylinder specifications are
indicated here. You will receive information that is more detailed if you
edit the respective partition).
Type of partition
While BOOTMENU is installed, you can modify the partitions only by editing the BOOTMENU partitiontable.
SEE ALSO: ?
Edit
Partition
BOOTMENU
Partitiontable
Open
Save
Registration
SETUP PROGRAM:
Help / Registration...
Here you can type in your registration key, which you will receive after ordering. G
This registration key always consists of an "Identifier" and a "key."
You can register both of the setup programs (DOS and Windows) as well as the perhaps installed bootmanager by clicking on "OK." Only after the registration is complete is it possible to use the program without limitations and/or restrictions.
All future installations performed with this program (EXE file) will be executable afterwards without any restrictions as well.
SEE ALSO: T
Shareware
(Restictions)
Updates
Order
Copyright
Support
Liability
Warranty
Shareware (Restrictions)
The bootmanager BOOTMENU is shareware. That means you may test and evaluate this program free of charge and pass it along to other interested users as well. Proper and standard use, however, requires a registration of the program (you have to purchase the bootmanager BOOTMENU). This is valid for the setup program as well as the actual bootmanager (bootstrap).
Without a registration key, you can use this version without any restrictions for four weeks. AFTER the trial period is over, each boot will result in a registration notice being shown on your screen. With each booting of an unregistered copy, the registration notice will remain on your screen for one second longer. Example: AFTER the trial time has expired, the 10th booting will result in a ten-second delay before your system will actually start.
ONE license is required for EACH computer using the bootmanager BOOTMENU! If several licenses are ordered, it is possible to obtain a key for all licenses.
SEE ALSO: G
Registration
Order
Copyright
Support
Liability
Warranty
Order
You can order the bootmanager either by using the enclosed order form ORDER.TXT or online on the Internet. L
All other ordering details and prices can be found on the ordering form. n
Currently, all updates are FREE! Updates may be downloaded from the Internet whenever they become available.
SEE ALSO: D
Shareware
Registration
Copyright
Support
Liability
Warranty
Copyright / Support
Copyright (C) 1997-1998 of the bootmanager BOOTMENU rests with:
Ingenieurb
ro Hoyer
Hopfenweg 207
22851 Norderstedt
Germany
http://www.BOOTMENU.com/
Support@BOOTMENU.com
Fax:+49 (40) 52 95 06 07
Tel:+49 (40) 52 95 06 06
SEE ALSO: $
Liability
Warranty
Order
All listed trademarks are property of their respective owner(s)!
Liability / Warranty
If this program is used improperly, it may result in the IRRETRIEVABLE DESTRUCTION OF ALL DATA ON YOUR HARD DISK DRIVE!
It is thus absolutely necessary to create a backup before using the bootmanager BOOTMENU. According to the ruling by the district court Konstanz 1 S 292/95 from May 10 1997, daily data backup is REASONABLE and can be EXPECTED! j
THUS, ANY RESPONSIBILITY OR LIABILITY FOR ANY LOSSES OR DAMAGES IS NOT ACCEPTED! UNDER NO CIRCUMSTANCES! 8
The purchase of this software is according to the BGB
494 a "TRIAL PURCHASE" (German Federal Legal Code). This means that the software can be evaluated BEFORE the actual purchase. The software is provided AS IS without warranty of any kind. Any rights for modifications or follow-up corrections DO NOT exist. w
Should you find any errors, please let our support staff know and we will try to correct the error within a few days. q
Any bug notifications (if not already known) and all good ideas will be rewarded with a free registration key!
SEE ALSO:
Copyright
Support
Updates
History of Development
The following overview shows the development history of the bootmanager BOOTMENU:
4.2X 8
Command Line Options available in the Windows Version.
4.1X D
A freely definable opening message can be displayed while booting.
4.0X 0
Windows 95/98/NT version of the setup program.
3.7X }
Command line options are supported.
Boot images may be hidden.
The contents of entire partitions may be stored as a file.
3.6X
Changes of the partition type are automatically recognized and copied from
the MBR to the BOOTMENU partitiontable.
BOOTMENU's colors may be changed.
3.5X 6
Secondary partitions (logical drives) are supported.
3.3X 9
Hard disk drives larger than 8 gigabytes are supported.
3.2X r
The positions of the partition entries within the master boot record
partitiontable can be selected as desired.
3.1X p
The boot images can fill the keyboard buffer.
Selection of boot images in BOOTMENU by typing in first letter.
3.0X ,
Extension to cover four hard disk drives.
2.9X ,
Password protection for the setup program.
2.8X m
Implementation of the password protection.
Implementation of the checksum function for master boot record.
2.5X
Improved input of boot images.
2.3X B
Implementation of the uninstall function with default bootstrap.
2.2X e
Internet distribution with homepage.
Implementation of a demo version with limited trial run time.
2.0X
Implementation of additional partitiontable:
Extension to cover 15 primary partitions.
Implementation of boot images to select an entire partitiontable.
New user interface for setup program.
1.7X :
Implementation of being able to boot from 2nd disk (B:).
1.6X Y
Saving of old selection and implementation of the auto-boot function
without keyboard.
1.4X /
Implementation of booting from 1st disk (A:).
1.2X J
Selection of active partition using a selection menu (with cursor keys).
1.1X (
Input function to edit partitiontable.
1.0X I
First functional version, selection of active partition using a number.
(.txt)